OCPBUGS-87371: Updating nmstate-console-plugin-container image to be consistent with ART for 5.0 by openshift-bot · Pull Request #227 · openshift/nmstate-console-plugin

openshift-bot · 2026-06-06T17:46:27Z

Updating nmstate-console-plugin-container image to be consistent with ART for 5.0
TLDR:
Product builds by ART can be configured for different base and builder images than corresponding CI
builds. This automated PR requests a change to CI configuration to align with ART's configuration;
please take steps to merge it quickly or contact ART to coordinate changes.

The configuration in the following ART component metadata is driving this alignment request:
nmstate-console-plugin.yml.

Detail:

This repository is out of sync with the downstream product builds for this component. The CI
configuration for at least one image differs from ART's expected product configuration. This should
be addressed to ensure that the component's CI testing accurate reflects what customers will
experience.

Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a
different version, usually prior to GA. The intent is to effect changes in both configurations
simultaneously without breaking either CI or ART builds, so usually ART builds are configured to
consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may
also configure changes in GA releases with CI remaining canonical for a brief grace period to enable
CI to succeed and the alignment PR to merge. In either case, ART configuration will be made
canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is
important to align CI configuration as soon as possible.

PRs are also triggered when CI configuration changes without ART coordination, for instance to
change the number of builder images or to use a different golang version. These changes should be
coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated
first to enable the changes to occur simultaneously in both CI and ART at the same time. This also
gives ART a chance to validate the intended changes first. For instance, ART compiles most
components with the Golang version being used by the control plane for a given OpenShift release.
Exceptions to this convention (i.e. you believe your component must be compiled with a Golang
version independent from the control plane) must be granted by the OpenShift staff engineers and
communicated to the ART team.

Roles & Responsibilities:

Component owners are responsible for ensuring these alignment PRs merge with passing
tests OR that necessary metadata changes are reported to the ART team
in #forum-ocp-art on Slack. If necessary, the changes required by this pull request can be
introduced with a separate PR opened by the component team. Once the repository is aligned,
this PR will be closed automatically.
In particular, it could be that a job like verify-deps is complaining. In that case, please open
a new PR with the dependency issues addressed (and base images bumped). ART-9595 for reference.
Patch-manager or those with sufficient privileges within this repository may add
any required labels to ensure the PR merges once tests are passing. In cases where ART config is
canonical, downstream builds are already being built with these changes, and merging this PR
only improves the fidelity of our CI. In cases where ART config is not canonical, this provides
a grace period for the component team to align their CI with ART's configuration before it becomes
canonical in product builds.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:

build_root:
  from_repository: true

Change behavior of future PRs:

In case you just want to follow the base images that ART suggests, you can configure additional labels to be
set up automatically. This means that such a PR would merge without human intervention (and awareness!) in the future.
To do so, open a PR to set the auto_label attribute in the image configuration. Example
You can set a commit prefix, like UPSTREAM: <carry>: . An example.

If you have any questions about this pull request, please reach out in the #forum-ocp-art Slack channel.

… ART for 5.0 Reconciling with https://github.com/openshift-eng/ocp-build-data/tree/7691ed4dc0b6585b358f9e73fb736ace9a48a286/images/nmstate-console-plugin.yml

openshift-bot · 2026-06-06T17:46:29Z

Created by ART pipeline job run https://art-jenkins.apps.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/aos-cd-builds/job/build%252Fsync-ci-images/201

coderabbitai · 2026-06-06T17:46:38Z

Walkthrough

This PR updates base container images from OpenShift 4.22 to OpenShift 5.0 across CI configuration and the Dockerfile. The Go runtime is also advanced from version 1.25 to 1.26 in the release image.

Changes

Upgrade to OpenShift 5.0 base images

Layer / File(s)	Summary
CI and container base image updates `.ci-operator.yaml`, `Dockerfile.art`	Release root image tag updated from `rhel-9-release-golang-1.25-openshift-4.22` to `rhel-9-release-golang-1.26-openshift-5.0` in the CI operator configuration. Dockerfile Node.js builder stage upgraded from `ocp/builder:rhel-9-base-nodejs-openshift-4.22` to `ocp/builder:rhel-9-base-nodejs-openshift-5.0`. Nginx runtime stage upgraded from `ocp/4.22:base-rhel9` to `ocp/5.0:base-rhel9`.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

openshift/nmstate-console-plugin#172: Both PRs modify the same .ci-operator.yaml release root image tag (build_root_image.tag/tag in openshift/release CI configuration), updating the base OpenShift/RHEL release image version to a newer rhel-9-release-golang-* tag.

Suggested reviewers

vojtechszocs
yaacov
gouyang

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	All test names in the PR use static, descriptive strings without dynamic content (no generated IDs, timestamps, pod/node/namespace names, or template variables).
Test Structure And Quality	✅ Passed	This PR contains no Ginkgo test code—it only updates CI configuration (.ci-operator.yaml) and Docker build files (Dockerfile.art). The check is not applicable to this codebase.
Microshift Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added in this PR. Changes are infrastructure-only: CI configuration and Dockerfile image tag updates. Check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This PR updates CI configuration and Dockerfile tags; it contains no Ginkgo e2e tests, making the SNO compatibility check inapplicable.
Topology-Aware Scheduling Compatibility	✅ Passed	PR only modifies CI configuration and Dockerfile base image tags. No deployment manifests, operator code, or controllers are added/modified, so topology-aware scheduling check is not applicable.
Ote Binary Stdout Contract	✅ Passed	Pull request is not applicable to OTE Binary Stdout Contract check—it only updates CI configuration files and container image tags, with no Go code or process-level logging modifications.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No Ginkgo e2e tests are added in this PR. The changes are configuration updates to .ci-operator.yaml and Dockerfile.art only. The check is not applicable.
No-Weak-Crypto	✅ Passed	PR contains only infrastructure changes (CI image tag updates). No cryptographic code or weak algorithms introduced.
Container-Privileges	✅ Passed	No container privilege escalation flags found. Dockerfile.art uses non-root user (1001) in runtime stage and root only for justified build compilation steps. No privileged settings in manifests.
No-Sensitive-Data-In-Logs	✅ Passed	No logging statements were added or modified. Changes are only image tag updates in CI configuration and Dockerfile, with no sensitive data exposure patterns.
Title check	✅ Passed	The title accurately describes the main change: updating container image tags for the nmstate-console-plugin to align with ART's OpenShift 5.0 configuration.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

openshift-ci · 2026-06-06T17:46:43Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-bot
Once this PR has been reviewed and has the lgtm label, please assign avivtur for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci-robot · 2026-06-06T17:46:46Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-87371, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Updating nmstate-console-plugin-container image to be consistent with ART for 5.0
TLDR:
Product builds by ART can be configured for different base and builder images than corresponding CI
builds. This automated PR requests a change to CI configuration to align with ART's configuration;
please take steps to merge it quickly or contact ART to coordinate changes.

The configuration in the following ART component metadata is driving this alignment request:
nmstate-console-plugin.yml.

Detail:

This repository is out of sync with the downstream product builds for this component. The CI
configuration for at least one image differs from ART's expected product configuration. This should
be addressed to ensure that the component's CI testing accurate reflects what customers will
experience.

Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a
different version, usually prior to GA. The intent is to effect changes in both configurations
simultaneously without breaking either CI or ART builds, so usually ART builds are configured to
consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may
also configure changes in GA releases with CI remaining canonical for a brief grace period to enable
CI to succeed and the alignment PR to merge. In either case, ART configuration will be made
canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is
important to align CI configuration as soon as possible.

PRs are also triggered when CI configuration changes without ART coordination, for instance to
change the number of builder images or to use a different golang version. These changes should be
coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated
first to enable the changes to occur simultaneously in both CI and ART at the same time. This also
gives ART a chance to validate the intended changes first. For instance, ART compiles most
components with the Golang version being used by the control plane for a given OpenShift release.
Exceptions to this convention (i.e. you believe your component must be compiled with a Golang
version independent from the control plane) must be granted by the OpenShift staff engineers and
communicated to the ART team.

Roles & Responsibilities:

Component owners are responsible for ensuring these alignment PRs merge with passing
tests OR that necessary metadata changes are reported to the ART team
in #forum-ocp-art on Slack. If necessary, the changes required by this pull request can be
introduced with a separate PR opened by the component team. Once the repository is aligned,
this PR will be closed automatically.

In particular, it could be that a job like verify-deps is complaining. In that case, please open
a new PR with the dependency issues addressed (and base images bumped). ART-9595 for reference.

Patch-manager or those with sufficient privileges within this repository may add
any required labels to ensure the PR merges once tests are passing. In cases where ART config is
canonical, downstream builds are already being built with these changes, and merging this PR
only improves the fidelity of our CI. In cases where ART config is not canonical, this provides
a grace period for the component team to align their CI with ART's configuration before it becomes
canonical in product builds.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:
build_root:
 from_repository: true
Change behavior of future PRs:

In case you just want to follow the base images that ART suggests, you can configure additional labels to be
set up automatically. This means that such a PR would merge without human intervention (and awareness!) in the future.
To do so, open a PR to set the auto_label attribute in the image configuration. Example

You can set a commit prefix, like UPSTREAM: <carry>: . An example.

If you have any questions about this pull request, please reach out in the #forum-ocp-art Slack channel.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-ci-robot · 2026-06-06T17:47:16Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-87371, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Updating nmstate-console-plugin-container image to be consistent with ART for 5.0
TLDR:
Product builds by ART can be configured for different base and builder images than corresponding CI
builds. This automated PR requests a change to CI configuration to align with ART's configuration;
please take steps to merge it quickly or contact ART to coordinate changes.

The configuration in the following ART component metadata is driving this alignment request:
nmstate-console-plugin.yml.

Detail:

This repository is out of sync with the downstream product builds for this component. The CI
configuration for at least one image differs from ART's expected product configuration. This should
be addressed to ensure that the component's CI testing accurate reflects what customers will
experience.

Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a
different version, usually prior to GA. The intent is to effect changes in both configurations
simultaneously without breaking either CI or ART builds, so usually ART builds are configured to
consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may
also configure changes in GA releases with CI remaining canonical for a brief grace period to enable
CI to succeed and the alignment PR to merge. In either case, ART configuration will be made
canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is
important to align CI configuration as soon as possible.

PRs are also triggered when CI configuration changes without ART coordination, for instance to
change the number of builder images or to use a different golang version. These changes should be
coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated
first to enable the changes to occur simultaneously in both CI and ART at the same time. This also
gives ART a chance to validate the intended changes first. For instance, ART compiles most
components with the Golang version being used by the control plane for a given OpenShift release.
Exceptions to this convention (i.e. you believe your component must be compiled with a Golang
version independent from the control plane) must be granted by the OpenShift staff engineers and
communicated to the ART team.

Roles & Responsibilities:

Component owners are responsible for ensuring these alignment PRs merge with passing
tests OR that necessary metadata changes are reported to the ART team
in #forum-ocp-art on Slack. If necessary, the changes required by this pull request can be
introduced with a separate PR opened by the component team. Once the repository is aligned,
this PR will be closed automatically.

In particular, it could be that a job like verify-deps is complaining. In that case, please open
a new PR with the dependency issues addressed (and base images bumped). ART-9595 for reference.

Patch-manager or those with sufficient privileges within this repository may add
any required labels to ensure the PR merges once tests are passing. In cases where ART config is
canonical, downstream builds are already being built with these changes, and merging this PR
only improves the fidelity of our CI. In cases where ART config is not canonical, this provides
a grace period for the component team to align their CI with ART's configuration before it becomes
canonical in product builds.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:
build_root:
 from_repository: true
Change behavior of future PRs:

In case you just want to follow the base images that ART suggests, you can configure additional labels to be
set up automatically. This means that such a PR would merge without human intervention (and awareness!) in the future.
To do so, open a PR to set the auto_label attribute in the image configuration. Example

You can set a commit prefix, like UPSTREAM: <carry>: . An example.

If you have any questions about this pull request, please reach out in the #forum-ocp-art Slack channel.

Summary by CodeRabbit

Chores

Updated build infrastructure dependencies to newer versions for improved performance and security.

Upgraded Node.js build environment and web server runtime images to latest supported versions.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Dockerfile.art`:
- Line 2: Change the base image reference in the FROM line that currently uses
registry.ci.openshift.org (the "FROM
registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-5.0 AS build"
entry) to an approved Red Hat catalog image from catalog.redhat.com (use the UBI
minimal or distroless variant appropriate for NodeJS), keeping a floating tag
style (no immutable digest) and equivalent platform (e.g., UBI9 NodeJS image),
so the Dockerfile uses a supported catalog.redhat.com base image instead of the
CI registry.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 737a25f8-f8f8-437a-a07f-eda73a50cdb9

📥 Commits

Reviewing files that changed from the base of the PR and between 11466ba and 8b0f78e.

📒 Files selected for processing (2)

.ci-operator.yaml
Dockerfile.art

coderabbitai · 2026-06-06T17:49:26Z

@@ -1,5 +1,5 @@
 # Builder container
-FROM registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-4.22 AS build
+FROM registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-5.0 AS build


⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Use supported Red Hat catalog base images instead of CI registry images.

Both updated FROM references still point to registry.ci.openshift.org/..., which violates the container base-image policy for Dockerfiles. Please switch these to approved images from catalog.redhat.com (while keeping floating tags for RH images).
As per coding guidelines, "**/{Dockerfile,Containerfile}*: Base image: UBI minimal or distroless from catalog.redhat.com."

Suggested direction

-FROM registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-5.0 AS build +FROM <catalog.redhat.com-approved-builder-image>:<floating-tag> AS build ... -FROM registry.ci.openshift.org/ocp/5.0:base-rhel9 +FROM <catalog.redhat.com-approved-runtime-image>:<floating-tag>

Also applies to: 14-14

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Dockerfile.art` at line 2, Change the base image reference in the FROM line that currently uses registry.ci.openshift.org (the "FROM registry.ci.openshift.org/ocp/builder:rhel-9-base-nodejs-openshift-5.0 AS build" entry) to an approved Red Hat catalog image from catalog.redhat.com (use the UBI minimal or distroless variant appropriate for NodeJS), keeping a floating tag style (no immutable digest) and equivalent platform (e.g., UBI9 NodeJS image), so the Dockerfile uses a supported catalog.redhat.com base image instead of the CI registry.

Source: Coding guidelines

openshift-bot · 2026-06-08T07:23:29Z

ART wants to connect issue OCPBUGS-87657 to this PR, but found it is currently hooked up to ['OCPBUGS-87371']. Please consult with #forum-ocp-art if it is not clear what there is to do.

pcbailey · 2026-06-11T11:55:40Z

/lgtm

pcbailey · 2026-06-11T11:56:08Z

/retest

openshift-ci · 2026-06-11T13:20:45Z

@openshift-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-tests	`8b0f78e`	link	true	`/test e2e-tests`

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

openshift-ci-robot · 2026-06-18T07:58:01Z

@openshift-bot: This pull request references Jira Issue OCPBUGS-87371, which is valid.

3 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @lkladnit

Details

In response to this:

Updating nmstate-console-plugin-container image to be consistent with ART for 5.0
TLDR:
Product builds by ART can be configured for different base and builder images than corresponding CI
builds. This automated PR requests a change to CI configuration to align with ART's configuration;
please take steps to merge it quickly or contact ART to coordinate changes.

The configuration in the following ART component metadata is driving this alignment request:
nmstate-console-plugin.yml.

Detail:

This repository is out of sync with the downstream product builds for this component. The CI
configuration for at least one image differs from ART's expected product configuration. This should
be addressed to ensure that the component's CI testing accurate reflects what customers will
experience.

Most of these PRs are opened as an ART-driven proposal to migrate base image or builder(s) to a
different version, usually prior to GA. The intent is to effect changes in both configurations
simultaneously without breaking either CI or ART builds, so usually ART builds are configured to
consider CI as canonical and attempt to match CI config until the PR merges to align both. ART may
also configure changes in GA releases with CI remaining canonical for a brief grace period to enable
CI to succeed and the alignment PR to merge. In either case, ART configuration will be made
canonical at some point (typically at branch-cut before GA or release dev-cut after GA), so it is
important to align CI configuration as soon as possible.

PRs are also triggered when CI configuration changes without ART coordination, for instance to
change the number of builder images or to use a different golang version. These changes should be
coordinated with ART; whether ART configuration is canonical or not, preferably it would be updated
first to enable the changes to occur simultaneously in both CI and ART at the same time. This also
gives ART a chance to validate the intended changes first. For instance, ART compiles most
components with the Golang version being used by the control plane for a given OpenShift release.
Exceptions to this convention (i.e. you believe your component must be compiled with a Golang
version independent from the control plane) must be granted by the OpenShift staff engineers and
communicated to the ART team.

Roles & Responsibilities:

Component owners are responsible for ensuring these alignment PRs merge with passing
tests OR that necessary metadata changes are reported to the ART team
in #forum-ocp-art on Slack. If necessary, the changes required by this pull request can be
introduced with a separate PR opened by the component team. Once the repository is aligned,
this PR will be closed automatically.

In particular, it could be that a job like verify-deps is complaining. In that case, please open
a new PR with the dependency issues addressed (and base images bumped). ART-9595 for reference.

Patch-manager or those with sufficient privileges within this repository may add
any required labels to ensure the PR merges once tests are passing. In cases where ART config is
canonical, downstream builds are already being built with these changes, and merging this PR
only improves the fidelity of our CI. In cases where ART config is not canonical, this provides
a grace period for the component team to align their CI with ART's configuration before it becomes
canonical in product builds.

ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image).
In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:
build_root:
 from_repository: true
Change behavior of future PRs:

In case you just want to follow the base images that ART suggests, you can configure additional labels to be
set up automatically. This means that such a PR would merge without human intervention (and awareness!) in the future.
To do so, open a PR to set the auto_label attribute in the image configuration. Example

You can set a commit prefix, like UPSTREAM: <carry>: . An example.

If you have any questions about this pull request, please reach out in the #forum-ocp-art Slack channel.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Updating nmstate-console-plugin-container image to be consistent with…

8b0f78e

… ART for 5.0 Reconciling with https://github.com/openshift-eng/ocp-build-data/tree/7691ed4dc0b6585b358f9e73fb736ace9a48a286/images/nmstate-console-plugin.yml

openshift-bot force-pushed the art-consistency-openshift-5.0-nmstate-console-plugin branch from 8e936db to 8b0f78e Compare June 6, 2026 17:46

openshift-bot changed the title ~~Updating nmstate-console-plugin-container image to be consistent with ART for 5.0~~ OCPBUGS-87371: Updating nmstate-console-plugin-container image to be consistent with ART for 5.0 Jun 6, 2026

openshift-ci Bot requested review from avivtur and upalatucci June 6, 2026 17:46

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jun 6, 2026

coderabbitai Bot reviewed Jun 6, 2026

View reviewed changes

openshift-bot assigned vojtechszocs Jun 7, 2026

openshift-bot added the verified Signifies that the PR passed pre-merge verification criteria label Jun 10, 2026

openshift-ci Bot assigned pcbailey Jun 11, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 11, 2026

openshift-ci Bot requested a review from lkladnit June 18, 2026 07:58

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

OCPBUGS-87371: Updating nmstate-console-plugin-container image to be consistent with ART for 5.0#227

OCPBUGS-87371: Updating nmstate-console-plugin-container image to be consistent with ART for 5.0#227
openshift-bot wants to merge 1 commit into
openshift:mainfrom
openshift-bot:art-consistency-openshift-5.0-nmstate-console-plugin

openshift-bot commented Jun 6, 2026 •

edited by openshift-ci Bot

Loading

Uh oh!

openshift-bot commented Jun 6, 2026

Uh oh!

coderabbitai Bot commented Jun 6, 2026 •

edited

Loading

Uh oh!

openshift-ci Bot commented Jun 6, 2026

Uh oh!

openshift-ci-robot commented Jun 6, 2026

Uh oh!

openshift-ci-robot commented Jun 6, 2026

Summary by CodeRabbit

Uh oh!

coderabbitai Bot left a comment

Uh oh!

coderabbitai Bot Jun 6, 2026

Uh oh!

openshift-bot commented Jun 8, 2026

Uh oh!

pcbailey commented Jun 11, 2026

Uh oh!

pcbailey commented Jun 11, 2026

Uh oh!

openshift-ci Bot commented Jun 11, 2026

Uh oh!

openshift-ci-robot commented Jun 18, 2026 •

edited by openshift-ci Bot

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

openshift-bot commented Jun 6, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-bot commented Jun 6, 2026

Uh oh!

coderabbitai Bot commented Jun 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Possibly related PRs

Suggested reviewers

Uh oh!

openshift-ci Bot commented Jun 6, 2026

Uh oh!

openshift-ci-robot commented Jun 6, 2026

Uh oh!

openshift-ci-robot commented Jun 6, 2026

Summary by CodeRabbit

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot Jun 6, 2026

Choose a reason for hiding this comment

Uh oh!

openshift-bot commented Jun 8, 2026

Uh oh!

pcbailey commented Jun 11, 2026

Uh oh!

pcbailey commented Jun 11, 2026

Uh oh!

openshift-ci Bot commented Jun 11, 2026

Uh oh!

openshift-ci-robot commented Jun 18, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

openshift-bot commented Jun 6, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Jun 6, 2026 •

edited

Loading

openshift-ci-robot commented Jun 18, 2026 •

edited by openshift-ci Bot

Loading